Signaling-less dynamic call setup and teardown by utilizing observed session state information

ABSTRACT

A system and methodology that facilitates signaling-less call setup and teardown by employing observed Quality of Experience (QoE) and resource demands is provided. Moreover, the system provides an environment for supersonic treatment of observed QoE and Quality of Service (QoS) demands for mobile applications. Specifically, a monitoring component is employed to determine session state information associated with a traffic flow, which includes observed QoE and resource demand data. The session state information is stored in a shared memory location and can be analyzed to modify and/or create a network policy for the traffic flow. The network policy is applied to one or more traffic flows to minimize signaling exchanges between a communication network and a mobile station.

TECHNICAL FIELD

The subject disclosure relates to wireless communications and, moreparticularly, to facilitating dynamic call setup and/or teardown basedon an observed Quality of Experience (QoE) and/or resource demand.

BACKGROUND

Advances in wireless telecommunications are rapidly increasing theutilization of mobile devices that handle communication of media anddata between users and providers. Typically, mobile devices haveconnected to mobile networks, such as a wireless wide area network(WWAN) employing a wireless connection (e.g. 2G/3G/3.5G/4G).Traditionally, voice services over wireless networks were provided bycircuit-switched (CS) systems wherein a dedicated channel was used foreach voice call. Although CS systems provide a guaranteed Quality ofService (QoS) in terms of end-to-end (ETE) delay for the voice traffic,the network is inefficiently utilized. This is because resources for thededicated channel are always reserved, even when communication is notcarried out over the channel.

In particular, traditional CS networks enable opening a circuit betweenparticipants at the beginning of a call and allocating the totalbandwidth on that circuit to the participants for the duration of thecall. If the participants need less bandwidth, the operator cannot sharethe allocated bandwidth with other users, or if they need morebandwidth, the operator is unable to provide additional bandwidth. Aswireless communications evolve, packet-switched (PS) networks have beendeveloped that provide operators extra flexibility to optimize coverage,call quality and data speed. PS networks typically stream one or morepackets (voice and/or data) to/from the user, by a route, which isdetermined based on an algorithm. Thus, the network operator canprioritize different types of packets according to user demand. However,the PS network imposes a ‘best-effort’ constraint on packet delivery.For example, the PS network employs best efforts to deliver packets totheir destination on time, but the PS network cannot guarantee theirarrival schedule.

In addition, the wireless environment and the mobility of users presentadditional challenges to packet delivery. For example, radio channelconditions between a device and the network can usually vary and thechannel can become better or worse over time. Thus, a constant Qualityof Service (QoS) is difficult to maintain over time. The traditionalsignaling approach provides a significant overhead with signalingexchanges among the networks and devices. Accordingly, call setup andtreatment is delayed and is not optimum. Further, for advanced dataservices in mobile communications, such as, but not limited to, email,streaming and/or video communication, the conventional systems do notprovide significant QoS support, leading to inefficient utilization ofnetwork resources.

SUMMARY

The following presents a simplified summary of the specification inorder to provide a basic understanding of some aspects of thespecification. This summary is not an extensive overview of thespecification. It is intended to neither identify key or criticalelements of the specification nor delineate any scope particularembodiments of the specification, or any scope of the claims. Its solepurpose is to present some concepts of the specification in a simplifiedform as a prelude to the more detailed description that is presentedlater.

The systems and methods disclosed herein, in one aspect thereof, canfacilitate dynamic adjustment of one or more traffic flows based in parton observed Quality of Experience (QoE) information and/or resourcedemand in a packet switched communication network. Typically, the systemcan observe conditions associated with a traffic flow and determinesession state information for the flow. As an example, the session stateinformation can include, but is not limited to, a session nameassociated with the flow, a mode of operation, a Quality of Experience(QoE) factor, observed QoE value, resource requirements, observednetwork states, etc. Further, the system can store the determinedsession state information in a shared database. The shared database canreside at source (e.g. UE, application), within network, within anexternal entity, and/or can be distributed. According to an embodiment,the stored information can be accessed by most any monitoring tool,which can update the stored information. According to anotherembodiment, the stored information can be pulled by most any schedulingtool and/or application, which can utilize the stored session stateinformation to make policy decisions.

In accordance with another aspect, a scheduling component can beemployed that can facilitate policy decisions based on an analysis ofthe information stored in the shared database. The policy decisions caninclude updating an existing policy and/or creating a new policy. In oneaspect, the scheduling component can dynamically apply the updated ornew policy to a flow or a group of flows based on the analysis.Moreover, updating the policy can include, but is not limited to,updating a Quality of Service (QoS) class for the flow or the group offlows, updating a mode of operation (e.g., setting an idle mode),applying back pressure on a set of flows when congestion is observed,updating amount of resources allocated to the flow, etc.

Yet another aspect of the disclosed subject matter relates to a methodthat can be employed to facilitate dynamic adjustment of a networkpolicy and efficient end-to-end (ETE) resource utilization based onobserved QoE data. Typically, session state data associated with atraffic flow (e.g., audio, video, data, multimedia, etc.) can bemonitored and stored in a shared database. The session state data caninclude, but is not limited to, observed QOE, network state dynamics,resource demands, and/or user/application/service provider preferences.In one aspect, the session state data can be pulled from the shareddatabase for example, periodically, dynamically, based on networkprovider and/or user preferences, based on a network policy, etc.Moreover, the pulled session state data can be analyzed and a networkpolicy can be updated based on the analysis. Further, the updatednetwork policy can be applied to a set of traffic flows to minimizesignaling between the communication network and mobile stations.

The following description and the annexed drawings set forth certainillustrative aspects of the specification. These aspects are indicative,however, of but a few of the various ways in which the principles of thespecification may be employed. Other advantages and novel features ofthe specification will become apparent from the following detaileddescription of the specification when considered in conjunction with thedrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system that facilitates storage ofobserved session state information associated with a traffic flow in awireless communication network.

FIG. 2 illustrates an example system that can be employed forsignaling-less dynamic call setup and teardown.

FIG. 3 illustrates an example system that can be employed to facilitatedynamic adjustment of one or more traffic flows based in part onobserved Quality of Experience (QoE) information.

FIG. 4 illustrates an example system that provides a shared memoryspace, which can store session state information associated with atraffic flow that can be utilized to dynamically adjust one or morenetwork policies.

FIG. 5 illustrates an example system, which facilitates automating oneor more features by employing an artificial intelligence mechanism inaccordance with the subject innovation.

FIG. 6 illustrates an example methodology that can be utilized tofacilitate minimizing the signaling exchanges among wirelesscommunication networks and mobile devices, during communication setupand/or teardown.

FIG. 7 illustrates an example methodology that facilitates dynamicallyadjusting one or more network policies and increasing end-to-end (ETE)resource utilization based on observed QoE data.

FIG. 8 illustrates an example methodology facilitates mitigating signalexchange and processing during dynamic call setup and/or teardown basedon an observed QoE and/or resource demands.

FIG. 9 illustrates an exemplary UMTS network that facilitates dynamiccall setup and/or teardown based on session state information inaccordance with the subject innovation.

FIG. 10 illustrates a block diagram of a computer operable to executethe disclosed communication architecture.

DETAILED DESCRIPTION

One or more embodiments are now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the various embodiments. It may be evident,however, that the various embodiments can be practiced without thesespecific details, e.g., without applying to any particular networkedenvironment or standard. In other instances, well-known structures anddevices are shown in block diagram form in order to facilitatedescribing the embodiments in additional detail.

As used in this application, the terms “component,” “module,” “system,”“interface,” “platform,” “service,” “framework,” “connector,” or thelike are generally intended to refer to a computer-related entity,either hardware, a combination of hardware and software, software, orsoftware in execution or an entity related to an operational machinewith one or more specific functionalities. For example, a component maybe, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a controller and the controller can be a component. One or morecomponents may reside within a process and/or thread of execution and acomponent may be localized on one computer and/or distributed betweentwo or more computers. As another example, an interface can include I/Ocomponents as well as associated processor, application, and/or APIcomponents.

Further, the various embodiments can be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips . . . ), opticaldisks (e.g., compact disk (CD), digital versatile disk (DVD) . . . ),smart cards, and flash memory devices (e.g., card, stick, key drive . .. ). Additionally it should be appreciated that a carrier wave can beemployed to carry computer-readable electronic data such as those usedin transmitting and receiving electronic mail or in accessing a networksuch as the Internet or a local area network (LAN). Of course, thoseskilled in the art will recognize many modifications can be made to thisconfiguration without departing from the scope or spirit of the variousembodiments.

In addition, the word “exemplary” is used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to present concepts in a concrete fashion. As usedin this application, the term “or” is intended to mean an inclusive “or”rather than an exclusive “or”. That is, unless specified otherwise, orclear from context, “X employs A or B” is intended to mean any of thenatural inclusive permutations. That is, if X employs A; X employs B; orX employs both A and B, then “X employs A or B” is satisfied under anyof the foregoing instances. In addition, the articles “a” and “an” asused in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or clear fromcontext to be directed to a singular form.

Moreover, terms like “user equipment,” “mobile station,” “mobile,”subscriber station,” “access terminal,” “terminal,” “handset,” “enddevice,” “mobile device,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point,” “base station,”“Node B,” “evolved Node B,” “home Node B (HNB),” and the like, areutilized interchangeably in the subject application, and refer to awireless network component or appliance that serves and receives data,control, voice, video, sound, gaming, or substantially any data-streamor signaling-stream from a set of subscriber stations. Data andsignaling streams can be packetized or frame-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” and the likeare employed interchangeably throughout the subject specification,unless context warrants particular distinction(s) among the terms. Itshould be appreciated that such terms can refer to human entities orautomated components supported through artificial intelligence (e.g., acapacity to make inference based on complex mathematical formalisms),which can provide simulated vision, sound recognition and so forth.

Traditional wireless communication systems employ a significant amountof signaling during call setup and teardown. The overhead associatedwith the signaling leads to delayed (and/or not optimum) applicationflows. The systems and methods disclosed herein provide an ability totreat application flows in optimum manner instead of utilizing massivesignaling overhead. In one example, end devices, for example, userequipment (UE), can update their session state information at a sourcein a distributed shared memory virtual address. The session stateinformation can include observed Quality of Experience (QoE) data, whichcan be collectively utilized by a scheduler in the network to updateand/or modify a flow, a service provider policy, etc. Accordingly,signaling overhead can be reduced and updates and/or adjustments to aQoE and/or Quality of Service (QoS) matrices can be performed withsimple updates to the matrices.

Aspects, features, or advantages of the subject innovation can beexploited in substantially any wireless communication technology; e.g.,Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), EnhancedGeneral Packet Radio Service (Enhanced GPRS), Third GenerationPartnership Project (3GPP) Long Term Evolution (LTE), Third GenerationPartnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB), High SpeedPacket Access (HSPA), or Zigbee. Additionally, substantially all aspectsof the subject innovation can be exploited in legacy telecommunicationtechnologies.

Referring initially to FIG. 1, there illustrated is an example system100 that facilitates storage of observed session state informationassociated with a traffic flow in a wireless communication network, inaccordance with an aspect of the subject system. Typically, system 100can include a monitoring component 102 that can be utilized to observeconditions associated with a traffic flow. It can be appreciated thatthe traffic can include, but is not limited to, voice, video, and/ordata traffic. In one aspect, the monitoring component 102 can determinesession state information associated with the traffic flow. As anexample, the session state information can include, but is not limitedto, a session name, a mode of operation, data indicating whether aQuality of Experience (QoE) factor is enabled or disabled, observed QoE,resource requirements, observed network states, etc.

According to an aspect, the observed QoE can be determined by monitoringthe traffic flow and analyzing various factors, such as, the number ofgood packets received by a user equipment (UE), a rate of receiving goodpackets, delay, jitter, bandwidth, frame rate, packet loss, and/or mostany information associated with an application on the UE. However,observed QoE determination is not limited to the aforementioned factorsand observed QoE can be determined based on location of UE, GPS data,user satisfaction, content of data delivered, etc. In one example,application specific QoE contract can be location specific, such as, butnot limited to, inside a building versus outside the building, in densemetro areas, etc.

In one embodiment, the monitoring component 102 can reside within a UE.In this case, the monitoring component 102 can observe QoE at the UE.For example, the monitoring component 102 can determine that the UE isnot receiving packets at a specific rate that is suitable forcommunication and/or providing user satisfaction, and/or can determinethat “X” number of packets were dropped, an/or can determine usersatisfaction based on explicit user input and/or user satisfaction canbe inferred, etc. In an additional or alternate embodiment, themonitoring component 102 can reside within the communication network,for example the core network. In this case, the monitoring component 102can apply one or more policies, for example, set by a service provider,to determine a QoE observed by a UE. Further, an application (e.g. atthe source) can also facilitate determination of observed QoE, sessionstate information, resource utilization information, and/or the like. Inone aspect, the monitoring component 102 can determine observed QoEbased on determination of various parameters, such as, but not limitedto, bandwidth, delay, jitter, packet loss, frame rate, content of data,location specifics, etc. For example, an application specific QoEcontract can be location specific, such as, based on location of UE(e.g., inside or outside a building, in a dense metro area, etc.). Inone example, the set of parameters for QoE determination can bespecified by the UE, application and/or network.

Furthermore, the system 100 can include a shared database 104 that canbe updated by the monitoring component 102. The shared database 104 canreside at source (e.g., UE), within network, within an external entity,and/or can be distributed. In particular, the shared database 104 caninclude mutual and/or shared memory locations, which can be updated byan application, a network, and/or a UE, with session state informationand can reside completely or partially in a source, an application, thenetwork or a UE. In one aspect, the shared database 104 can be accessedby most any monitoring tool, such as monitoring component 102, which canwrite to the memory. Additionally, most any tool and/or application canutilize shared locks to concurrently and/or simultaneously read thestored data and utilize the stored session state data to make a policydecision.

In one aspect, when the shared database 104 is within a UE, informationfrom the shared database 104 can be pulled by the communication networkin an aggregated form, periodically, dynamically, in real-time, etc. Inanother aspect, when the shared database 104 is within the communicationnetwork, the session state information can be stored in the shareddatabase 104 by a sample caching mechanism that can run in thebackground. Specifically, the shared database 104 can maintain sessionstate information, which can include observed QoE and resourcespecifications for each flow within the communication network. Themonitoring component 102 can update the stored information for each flowbased on the observations. Observed QoE and network state dynamics canalso be stored in the shared database 104.

In an aspect, the monitoring component 102 can change, update and/ormodify the session states stored in the shared database 104 withinspecified boundaries, for example, bandwidth can trotter between 0-1Meg, delay can be bounded between 100 ms and 200 ms, jitter can be setto specific range, observed QOE can be updated, network resourcerequirements can be specified, enforced polices can be set, UE locationcan be set (e.g., indoor, outdoor, home, work, vehicular, etc.).According to an embodiment, the information stored in shared database104, including observed QoE and/or resource requirements can be utilizedby a scheduler or application with a core network, to adjust the Qualityof Service (QoS) support associated with the flow based in part theobserved QoE. Further, the scheduler can also update routes, schedulesand/or network policies based on the observed QoE and/or resourcerequirements.

It can be appreciated that the shared database 104 can include volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory. By way of illustration, and not limitation,nonvolatile memory can include read only memory (ROM), programmable ROM(PROM), electrically programmable ROM (EPROM), electrically erasablePROM (EEPROM), or flash memory. Volatile memory can include randomaccess memory (RAM), which acts as external cache memory. By way ofillustration and not limitation, RAM is available in many forms such asstatic RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), doubledata rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM(SLDRAM), and direct Rambus RAM (DRRAM). The memory (e.g., data stores,databases) of the subject systems and methods is intended to comprise,without being limited to, these and any other suitable types of memory.

Referring to FIG. 2, there illustrated is an example system 200 that canbe employed for signaling-less dynamic call setup and teardown inaccordance with an aspect of the subject disclosure. It can beappreciated that the monitoring component 102 and shared database 104can include respective functionality, as more fully described herein,for example, with regard to system 100.

According to an aspect, the monitoring component 102 and/or shareddatabase 104 can reside within a UE and/or a communication network.Typically, the UE as disclosed herein can include most any communicationdevice employed by a subscriber, such as, but not limited to, a cellularphone, a personal digital assistant (PDA), a laptop, a personalcomputer, a media player, a gaming console, and the like. Moreover, theUE can access the communication network via most any radio technology.It can be appreciated that the communication network can include mostany radio environment, such as, but not limited to, Universal MobileTelecommunications System (UMTS), Global System for Mobilecommunications (GSM), LTE, WiFi, WiMAX, CDMA, etc.

As described previously, the monitoring component 102 can observe anddetermine session state information associated with a traffic flowbetween the communication network and the UE. Specifically, themonitoring component 102 can determine an observed QoE for a trafficflow, based on various factors, such as but not limited to, packetdelivery rate, dropped packet rate, frame rate, UE preferences, networkpreferences, application preferences, user input, delay, jitter,bandwidth, location specifics, etc. Further, the monitoring component102 can store the determined information within shared database 104. Inone aspect, the information stored in the shared database 104 caninclude, observed QoE 202, resource demands 204, and/or, user and/orapplication preferences 206. For example, the monitoring component 102can calculate an observed QoE that is experienced by an end user and canalso determine whether additional network resources can help improveQoE, for example beyond a specified threshold. The observed QoE 202 andresource demands 204 data can be stored by the monitoring component 102in the shared database 104. Further, user and/or application (or device)preferences (e.g., a user can set a preference in an application on theUE to receive a notification or alert each time an email is received)can be stored within 104.

System 200 further includes a scheduling component 208 that facilitatespolicy decisions based on an analysis of the information stored inshared database 104 that can adjust the traffic flow. In one aspect, thescheduling component 208 can apply one or more policies for a flow or agroup of flows depending on analysis. As an example, the schedulingcomponent 208 can update the QoS class, update the mode of operation(e.g., set an idle mode), apply backpressure on as set of flows whencongestion is observed (e.g., by the monitoring component 102), etc.,for the flow or group of flows. Typically, the observed QoE associatedwith a flow can continuously vary because of the wireless & mobilenature of communications. For example, when a UE is in motion, thesignal strength can change and observed QoE can change. System 200 canfacilitate observing the QoE (e.g., by the monitoring component 102) andaccordingly adapting one or more flows (e.g., by the schedulingcomponent 208).

Referring now to FIG. 3, there illustrated is an example system 300 thatcan be employed to facilitate dynamic adjustment of one or more trafficflows based in part on observed QoE information, according to an aspectof the subject disclosure. It can be appreciated that the monitoringcomponent 102, shared database 104 and scheduling component 208 caninclude respective functionality, as more fully described herein, forexample, with regard to systems 100 and 200. In one aspect, themonitoring component 102 and shared database 104 can be located within aUE 302. However, the subject application is not so limited and as notedpreviously, the monitoring component 102 and the shared database 104 canreside completely, partially, or be distributed between, UE 302, network304, an application or a third party entity (not shown).

Additionally, UE 302 can be, but is not required to be, for instance, acommunication device, a multi-mode device, a dual-mode device, adual-mode cellular/IP device, a mobile communication device, a cellulardevice that connects to a fixed IP network, a smartphone, a gamingdevice, a home media center, a portable media player, a satellite phone,a desktop device, a cellular phone, a portable gaming device, a mobilephone, a portable music player, a portable device, a laptop, a personaldigital assistant, or a handheld or combinations thereof that can employmost any wireless mobile communication technology to communicate withnetwork 304.

System 300 can typically include an aggregation component 306 that canbe utilized to aggregate information stored within the shared database104. It can be appreciated that although the aggregation component 306is illustrated to reside within the UE 302, the aggregation component306 can reside at most any location, such as, but not limited to, withinthe network 304, the scheduling component 208, and/or at a third partyentity (not shown). In one aspect, the aggregation component 306 cananalyze the information in the shared database 104 and select data thatcan be delivered to the scheduling component, in a manner such thatsignaling is reduced. As an example, the aggregation component 306 canidentify essential information associated with a traffic flow, which canbe utilized by the scheduling component 208 to make policy decisions.Further, the aggregation component 306 can also aggregate informationassociated with multiple flows and/or can sample the data associatedwith multiple flows from the shared database 104. Typically, themultiple flows can belong to a specific category, as explained in detailinfra.

The scheduling component 208 can utilize the aggregated information tocreate or update a policy associated with the traffic flow and/or withthe multiple traffic flows. According to an aspect, a data pullingcomponent 308 can be utilized to pull data from the aggregationcomponent 306. In one example, the pulling component 308 can pull datadepending on a service provider preference, such as, but not limited to,periodically or in real time. Typically, a network operator candetermine a time period for pulling data or the time period can beautomatically determined, for example, when the network is idle or whenavailable bandwidth is greater than a threshold. In one aspect, thescheduling component 208 can update one or more policies, such as, apolicy that determines allocation of resources, flow routes, QoSsupport, etc. based on an analysis of the received data. Moreover, anInternet Protocol (IP) architecture can be enhanced with real timesource and/or network initiated session state updates. In particular, asimple trigger protocol can be employed (e.g., by the data pullingcomponent 308) to synch up the state changes from the shared database104 with the network and vise versa. In one aspect, the data pullingcomponent 308 can sample data from different UEs for aggregationtreatment and the scheduling component 208 can modify one or morepolicies associated with disparate UEs based on the aggregation data.Additionally, the data pulling component 308 can pull the session stateupdates every interval and avoid massive signal processing performed inconventional systems. Accordingly, a faster steady state can be achievedby pulling session state information from the end devices and signalingexchanges among the networks and devices can be minimized. In addition,dynamic and QoS/QoE adaptation can be achieved in a distributed fashionand signaling overhead can be reduced, for example, by 10-100 folds.

FIG. 4 illustrates an example system 400 that provides a shared memoryspace, which can store session state information associated with atraffic flow that can be utilized to dynamically adjust one or morenetwork policies in accordance with the subject innovation. It can beappreciated that the shared database 104, scheduling component 208, UE302, and network 304 can include respective functionality, as more fullydescribed herein, for example, with regard to systems 100, 200 and 300.Further, monitoring component) (402) and monitoring component2 (404) canbe substantially similar to monitoring component 102 as more fullydisclosed herein, for example, with regard to systems 100, 200 and 300,and can include functionality thereof.

The shared database 104 included in system 400 can be updated bymonitoring component1 402 and/or monitoring component2 404. It can beappreciated that although the shared database 104 is depicted to resideon the network 304, the shared database can be located on the UE 302, ata third party entity, on a disparate network, and/or can be distributed.Moreover, monitoring component1 402 can determine session stateinformation associated with a traffic flow based on various factors,such as, but not limited to, the communication received at the UE 302,the location of the UE 302, motion of the UE 302, user input, etc.Further, the UE 302 can allocate a session state memory area when a callis initiated or terminated, and can update the session state dynamicsincluding the observed application QoE. According to one aspect, thedetermined information can be aggregated (e.g., by an aggregationcomponent 306) and can be pulled by the network and stored within theshared database 104, for example, periodically, dynamically, or based ona specified policy.

Additionally or alternately, the monitoring component2 404 can alsodetermine session state information associated with the traffic flow(and/or disparate traffic flows) and update the shared database 104. Asan example, monitoring component2 404 can be located most anywhere inthe network 304 and can determine session state information associatedwith a traffic flow based on most any proxy monitoring mechanism. Forexample, session state information associated with a flow can bedetermined based on a policy defined by a network operator, contentdelivery time, amount of data exchanged, etc. In one aspect, themonitoring component2 404 can classify traffic flows within network 304into multiple categories and can sample data associated with a subset offlows in each category. Moreover, the sampled data can be stored in theshared database 104. In one aspect, monitoring component2 404 can beuseful for monitoring traffic flows and determining session stateinformation for the traffic flows to UEs that do not include amonitoring component (not shown).

According to an embodiment, the scheduling component 208 can retrievedata associated with the traffic flow (and/or the subset of trafficflows) from the shared database 104 and can analyze the retrievedinformation. Based on the analysis, the scheduling component 208 cancreate a new network policy and/or update/delete an existing networkpolicy associated with the traffic flow and/or a set of disparatetraffic flows (e.g., that belong to the same category as the trafficflow). In one aspect, a network policy store 406 can be employed thatstores network policies associated with traffic flows in network 304.The network policy store 406 can be updated by the scheduling component208 based on an analysis of the data from shared database 104. As anexample, the scheduling component 208 can update a policy thatfacilitates allocation of resources, flow routes, QoS support, etc.associated with the traffic flows. Typically, the network policy store406 can include, and is not limited to, both volatile and nonvolatilememory, removable and non-removable memory.

Consider an example, wherein, the shared database 104 can store one ormore user preferences. Typically, applications (e.g. on UE 302) candecide what type of features the application can employ and/or decidethe signaling between the application and network 304. Oftentimes, thesedecisions can increase network traffic and lead to network performanceissues. For example, a user can set a preference via UE 302 to receive anotification from an email server when the user gets an email. However,when the volume of emails is large, the network 304 can easily getoverloaded. In this example scenario, the scheduling component 208 candetermine and/or modify a policy within the network policy store 406that can be enforced, such that the signaling is minimized andcongestion and/or network overload can be avoided. As an example, thescheduling component 208 can create/modify a policy, which can ensurethat signals from the email server can be aggregated, such that, anotification can be sent to the UE 302 when the network 304 is idle, orperiodically, or after “X” number of signals are received, (where “X”can be most any natural number from 1 to infinity), etc.

In another example scenario, an application can get aggressive wheninformation is not properly received at the UE 302 through the network304. Moreover, aggressive applications can retransmit signals too often,resulting in network congestion. The scheduling component 208 cancreate/modify a policy, which can ensure that the application isnotified of the current network status. Further, information stored inshared database 104, for example, observed QoE data, can be visible toboth the application and the network 304. Accordingly, based on ananalysis of the stored information, the scheduling component 208 canfacilitate adjusting network policies to apply backpressure, adjustbandwidth allocation, and/or request the application to back off whenthe network is busy. According to an aspect, the shared database 104provides the scheduling component 208 a view of UE behavior, whichfacilitates enhanced and optimized end-to-end (ETE) QOS and QOEtreatment. The scheduling component 208 can enable the networks 304 androuter nodes to drive their route updates from the UEs in their domains.In one aspect, the scheduling component 208 can interact independentlybased on its aggregation view of the session state information collectedfor ETE treatment.

FIG. 5 illustrates a system 500 that employs an artificial intelligence(AI) component 502, which facilitates automating one or more features inaccordance with the subject innovation. It can be appreciated that theshared database 104, scheduling component 208, monitoring component2404, network policy store 406, and network 304 can include respectivefunctionality, as more fully described herein, for example, with regardto systems 100, 200, 300 and 400. The subject innovation (e.g., inconnection with monitoring and/or analysis) can employ various AI-basedschemes for carrying out various aspects thereof. For example, a processfor determining an update to a policy stored in the network policy store406 can be facilitated via an automatic classifier system and process.

A classifier is a function that maps an input attribute vector, x=(x1,x2, x3, x4, xn), to a confidence that the input belongs to a class, thatis, f(x)=confidence(class). Such classification can employ aprobabilistic and/or statistical-based analysis (e.g., factoring intothe analysis utilities and costs) to prognose or infer an action that auser desires to be automatically performed. In the case of wirelesscommunication systems, for example, attributes can be derived frominformation stored in the shared database 104 and the classes can becategories or areas of interest (e.g., levels of priorities).

A support vector machine (SVM) is an example of a classifier that can beemployed. The SVM operates by finding a hypersurface in the space ofpossible inputs, which the hypersurface attempts to split the triggeringcriteria from the non-triggering events. Intuitively, this makes theclassification correct for testing data that is near, but not identicalto training data. Other directed and undirected model classificationapproaches include, e.g., naïve Bayes, Bayesian networks, decisiontrees, neural networks, fuzzy logic models, and probabilisticclassification models providing different patterns of independence canbe employed. Classification as used herein also is inclusive ofstatistical regression that is utilized to develop models of priority.

As will be readily appreciated from the subject specification, thesubject innovation can employ classifiers that are explicitly trained(e.g., via a generic training data) as well as implicitly trained (e.g.,via observing user behavior, receiving extrinsic information). Forexample, SVM's are configured via a learning or training phase within aclassifier constructor and feature selection module. Thus, theclassifier(s) can be used to automatically learn and perform a number offunctions, including but not limited to determining according to apredetermined criteria when the shared database can be updated, when andhow a network policy can be updated/created/deleted, etc. The criteriacan include, but is not limited to, observed QoE, resource demands,historical patterns, UE behavior, user preferences, service providerpreferences and/or policies, location of the UE, motion of the UE,network status, etc.

FIGS. 6-8 illustrate methodologies and/or flow diagrams in accordancewith the disclosed subject matter. For simplicity of explanation, themethodologies are depicted and described as a series of acts. It is tobe understood and appreciated that the subject innovation is not limitedby the acts illustrated and/or by the order of acts, for example actscan occur in various orders and/or concurrently, and with other acts notpresented and described herein. Furthermore, not all illustrated actsmay be required to implement the methodologies in accordance with thedisclosed subject matter. In addition, those skilled in the art willunderstand and appreciate that the methodologies could alternatively berepresented as a series of interrelated states via a state diagram orevents. Additionally, it should be further appreciated that themethodologies disclosed hereinafter and throughout this specificationare capable of being stored on an article of manufacture to facilitatetransporting and transferring such methodologies to computers. The termarticle of manufacture, as used herein, is intended to encompass acomputer program accessible from any computer-readable device, carrier,or media.

Referring now to FIG. 6, illustrated is an example methodology 600 thatcan be utilized to facilitate minimizing signaling exchanges amongnetworks and mobile devices, during communication setup and/or teardown.At 602, session state information associated with a traffic flow can bedetermined. As an example, the session state information can include,but is not limited to, a session name associated with the flow, a modeof operation, a QoE factor that indicates whether QoE is enabled ordisabled, an observed QoE, resource demand, an observed network state,etc. Further, it can be appreciated that the session state informationcan be determined by monitoring and/or observing the traffic flow,location and/or motion of the mobile device, user preferences, networkprovider preferences, and the like. Specifically, the monitoring and/orobserving can be performed on the network side, mobile device sideand/or by a third party entity. Moreover, the session state informationcan be stored in the shared memory location by employing a samplecaching mechanism that can run in the background.

At 604, a shared memory location can be updated with the determinedsession state information. The shared memory location can be read by oneor more decision making tool that can update a policy, modify allocationof resources, and/or adjust a route based on an analysis of the storedinformation. According to one aspect, the session state information canbe pulled, for example, by the network in an aggregated form,periodically, dynamically, in real-time, when network is idle, etc.

FIG. 7 illustrates an example methodology 700 that facilitatesdynamically adjusting one or more network policies and increasing ETEresource utilization based on observed QoE data, in accordance with anaspect of the subject specification. At 702, session state dataassociated with a traffic flow (e.g., audio, video, data, multimedia,etc.) can be received. In one aspect, the session state data can bepulled from an end device, and/or a shared database for example,periodically, dynamically, based on network provider and/or userpreferences, based on a network policy, etc. The session state data caninclude, but is not limited to, observed QoE, network state dynamics,resource demands, and/or user/application/service provider preferences.As an example, the observed QoE can be determined based on determiningvarious parameters associated with the traffic flow, such as, but notlimited to, packet delivery rate, dropped packet rate, frame rate, UEpreferences, network preferences, application preferences, user input,delay, jitter, bandwidth, location specifics, etc. Typically, theapplication and/or network can agree on a QoE parameter set.

At 704, the received session state data can be analyzed. Further, at 706one or more network policies can be updated based on the analysis.Furthermore, at 708, the one or more updated policies can be applied toa set of traffic flows to minimize signaling between the communicationnetwork and end device. For example, a QoS class for a flow or group offlows can be updated, a mode of operation (e.g., set an idle mode) canbe set and/or changed, resource allocation can be changed, backpressurecan be applied (when congestion is observed), etc.

FIG. 8 illustrates an example methodology 800 that facilitatesmitigating signal exchange and processing during dynamic call setupand/or teardown based on an observed Quality of Experience (QoE) and/orresource demands, according to an aspect of the subject disclosure. At802, communication sessions can be categorized. In one aspect, sessionswith one or more common or similar properties can be grouped in the samecategory. At 804, QoE and/or resource demand DATA can be sampled in eachcategory. Specifically, an observed QoE and/or resource demandassociated with one or more sample sessions can be determined. Morespecifically, the sampled data can be analyzed and a network policy canbe created and/or adjusted based on the analysis. At 806, the networkpolicy can be applied to a set of sessions in the category. For example,data, including observed QoE and/or resource demand, associated with aparticular session (e.g., session number 7), can be determined and apolicy can be updated based on an analysis of the data. The updatedpolicy can be applied to set of sessions (e.g., session numbers 7, 12,and 22) and/or all the sessions in the category.

FIG. 9 illustrates an exemplary UMTS network 900 that facilitatesdynamic call setup and/or teardown based on session state information inaccordance with the subject innovation. The architecture is based on the3GPP (Third Generation Partnership Project) Release 99 specification.However, it is to be understood that the subject innovation can beapplied to any UMTS telecommunications architecture, including by way ofexample, Release 5 (R5) and, R5 and Release 6 (R6) 3GPP standards. UMTSoffers teleservices (e.g., speech and/or SMS-Short Message Service) andbearer services, which provide the capability for information transferbetween access points. Negotiation and renegotiation of thecharacteristics of a bearer service can be performed at session orconnection establishment, and during an ongoing session or connection.Both connection oriented and connectionless services can be offered forpoint-to-point and point-to-multipoint communications.

The following frequencies 1885-2025 MHz and 2110-2200 MHz can beallocated for UMTS use. However, the innovative aspects described hereincan also be applied to other frequency bands. Bearer services can havedifferent QoS (quality-of-service) parameters for maximum transferdelay, delay variation and bit error rate. Offered data rate targetsare: 144 kbps satellite and rural outdoor; 384 kbps urban outdoor; and2048 kbps indoor and low range outdoor.

UMTS network services can have different QoS classes for four types oftraffic: conversational class (e.g., voice, video telephony, videogaming); streaming class (e.g., multimedia, video on demand, webcast);interactive class (e.g., web browsing, network gaming, database access);and background class (e.g., email, SMS, downloading). UMTS can alsosupport have a virtual home environment, which is a concept forportability across network boundaries and between terminals in apersonal service environment. Personal service environment means thatusers are consistently presented with the same personalized features,user interface customization and services in whatever network orterminal, wherever the user may be located. UMTS also includes networksecurity and location based services.

The UMTS network 900 can consist of three interacting domains; a userequipment (UE) domain 902, a UMTS Terrestrial Radio Access Network(UTRAN) domain 904, and a core network (CN) domain 906. The UTRAN domain904 is also referred to as the access network domain and the CN 906 isreferred to as the core network domain, the both of which comprise aninfrastructure domain.

The UE domain 902 includes a USIM (user services identity module) domainand an ME (mobile equipment) domain. User equipment is the equipmentused by the user to access UMTS services. In the UE domain 902, the UMTSIC card is the USIM 908, which has the same physical characteristics asGSM SIM (subscriber identity module) card. The USIM interfaces to ME 910via a Cu reference point. Functions of the USIM include: support of oneUSIM application (and optionally, more than one); support of one or moreuser profiles on the USIM; update of USIM specific information over theair; security functions; user authentication; optional inclusion ofpayment methods; and optional secure downloading of new applications.

UE terminals work as an air interface counter part for Node-B devices ofthe access network and have many different types of identities.Following are some of the UMTS identity types, which are taken directlyfrom GSM specifications: international mobile subscriber identity(IMSI); temporary mobile subscriber identity (TMSI); packet temporarymobile subscriber identity (P-TMSI); temporary logical link identity(TLLI); mobile station ISDN (MSISDN); international mobile stationequipment identity (IMEI); and international mobile station equipmentidentity and software version number (IMEISV).

A UMTS mobile station (MS) can operate in one of three modes ofoperation. A PS/CS mode of operation is where the MS is attached to boththe PS (packet-switched) domain and CS (circuit-switched) domain, andthe MS is capable of simultaneously operating PS services and CSservices. A PS mode of operation is where the MS is attached to the PSdomain only, and can only operate services of the PS domain. However,this does not prevent CS-like services from being offered over the PSdomain (e.g., VoIP). In a third CS mode of operation, the MS is attachedto the CS domain only, and can only operate services of the CS domain.

The UTRAN 904 provides the air interface access method for the UE domain902. The reference point between the UE domain and the infrastructuredomain is the Uu UMTS radio interface. The access network domainprovides the physical entities that manage resources of the accessnetwork and facilitates access to the core network domain. In UMTSterminology, a base station of the access network domain is referred asa Node-B device 912, and control equipment for Node-B devices is calleda radio network controller (RNC) 914. The interface between the Node-Bdevice and the RNC 914 is the IuB interface. The interface between twoRNCs is called the Iur interface. According to an aspect, the adaptiveR99 CS and CS over HSPA Link diversity that facilitates enhancedcoverage and capacity, described in detail supra, can be implemented inthe UTRAN 904.

The functions of Node-B devices include: air interfacetransmission/reception; modulation and demodulation; CDMA (Code DivisionMultiple Access) physical channel coding; micro diversity; errorhanding; and closed loop power control. The functions of the RNCinclude: radio resource control; admission control; channel allocation;power control settings; handover control; macro diversity; ciphering;segmentation and reassembly; broadcast signaling; and open loop powercontrol.

Wideband CDMA (WCDMA) technology was selected for UTRAN air interface.UMTS WCDMA is a direct sequence CDMA system where user data ismultiplied with quasi-random bits derived from WCDMA spreading codes. InUMTS, in addition to channelization, codes are used for synchronizationand scrambling. WCDMA has two basic modes of operation: frequencydivision duplex (FDD) and time division duplex (TDD).

The Core Network is divided in circuit-switched and packet-switcheddomains. Some of the circuit-switched elements are a mobile servicesswitching center (MSC) and visitor location register (VLR) 916 andgateway MSC (GMSC) 918. Packet-switched elements include a serving GPRSsupport node (SGSN) 920 and gateway GPRS support node (GGSN) 922. Somenetwork elements such as an EIR (equipment identity register) (notshown), HLR (home location register) 924, VLR and AuC (authenticationcenter) (not shown) can be shared by both domains.

A function of the CN 902 is to provide switching, routing and transitfor user traffic. The CN 902 also contains the databases and networkmanagement functions. The basic CN architecture for UMTS is based on theGSM network with GPRS (general packet radio service) capability. Allequipment is modified for UMTS operation and services. The radio accessnetwork has several interfaces that can be configured and dimensioned.The CN 906 interfaces to the radio access domain via an Iu interface. AnIu-CS (circuit-switched) reference point interfaces an RNC of the accessnetwork to the MSC/VLR entity 916 of the CN 906 for voice from/to theMSC/VLR 916. An Iu-PS (packet-switched) reference point interfaces anRNC of the access network to the SGSN entity 920 of the CN 906 for datafrom/to the SGSN 920.

In the CN 906, a Gs interface is provided between the MSC/VLR 916 andthe SGSN. A Gn interface is provided between the SGSN 920 and the GGSN922. A D interface is provided between the MSC/VLR 916 and the HLR 924,and the HLR 924 and the GMSC 918. A Gr interface is provided between theSGSN 920 and the HLR 924. A Gc interface is provided between the GGSN922 and the HLR 924.

The CN 906 provides the interface from the UE domain 902 to externalnetworks 926 such as the Internet 928 via a Gi interface from the GGSN922, and other networks 930 via the GMSC 918, which can include a PLMN(public land mobile network), PSTN (public switched telephone network)and ISDN (integrated service digital network) networks.

Asynchronous Transfer Mode (ATM) is defined for UMTS core transmission.ATM Adaptation Layer type 2 (AAL2) handles circuit-switched connection,and packet connection protocol AAL5 is designed for data delivery.

The architecture of the CN 906 can change when new services and featuresare introduced. Number Portability Database (NPDB), for example, can beused to enable a user to change the network while keeping their oldphone number. A gateway location register (GLR) can be employed tooptimize the subscriber handling between network boundaries.Additionally, the MSC/VLR and SGSN can merge to become a UMTS MSC.

Summarizing the UMTS frequencies, 1920-1980 MHz and 2130-2170 MHz areemployed for FDD and WCDMA. Paired uplink and downlink channel spacingcan be 5 MHz and raster is 200 kHz. An operator can use 3-4 channels(2×15 MHz or 2×20 MHz) to build a high-speed, high-capacity network.Frequencies 1900-1920 MHz and 2010-2025 MHz are for TDD and TD/CDMA.Unpaired channel spacing can be 5 MHz and raster is 200 kHz. Transmitand receive are not separated in frequency. Frequencies 1980-2010 MHzand 2170-2200 MHz are employed for satellite uplink and downlink.

Referring now to FIG. 10, there is illustrated a block diagram of acomputer operable to execute the disclosed communication architecture.In order to provide additional context for various aspects of thesubject specification, FIG. 10 and the following discussion are intendedto provide a brief, general description of a suitable computingenvironment 1000 in which the various aspects of the specification canbe implemented. While the specification has been described above in thegeneral context of computer-executable instructions that can run on oneor more computers, those skilled in the art will recognize that thespecification also can be implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the specification can also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

A computer typically includes a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the computer and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media includes volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information such as computer-readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disk (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

With reference again to FIG. 10, the example environment 1000 forimplementing various aspects of the specification includes a computer1002, the computer 1002 including a processing unit 1004, a systemmemory 1006 and a system bus 1008. The system bus 1008 couples systemcomponents including, but not limited to, the system memory 1006 to theprocessing unit 1004. The processing unit 1004 can be any of variouscommercially available processors. Dual microprocessors and othermulti-processor architectures can also be employed as the processingunit 1004.

The system bus 1008 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1006includes read-only memory (ROM) 1010 and random access memory (RAM)1012. A basic input/output system (BIOS) is stored in a non-volatilememory 1010 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1002, such as during start-up. The RAM 1012 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1002 further includes an internal hard disk drive (HDD)1014 (e.g., EIDE, SATA), which internal hard disk drive 1014 can also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1016, (e.g., to read from or write to aremovable diskette 1018) and an optical disk drive 1020, (e.g., readinga CD-ROM disk 1022 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1014, magnetic diskdrive 1016 and optical disk drive 1020 can be connected to the systembus 1008 by a hard disk drive interface 1024, a magnetic disk driveinterface 1026 and an optical drive interface 1028, respectively. Theinterface 1024 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE 1394 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject specification.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1002, the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer, such as zipdrives, magnetic cassettes, flash memory cards, cartridges, and thelike, can also be used in the example operating environment, andfurther, that any such media can contain computer-executableinstructions for performing the methods of the specification.

A number of program modules can be stored in the drives and RAM 1012,including an operating system 1030, one or more application programs1032, other program modules 1034 and program data 1036. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1012. It is appreciated that the specification can beimplemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 1002 throughone or more wired/wireless input devices, e.g., a keyboard 1038 and apointing device, such as a mouse 1040. Other input devices (not shown)can include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1004 through an input deviceinterface 1042 that is coupled to the system bus 1008, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1044 or other type of display device is also connected to thesystem bus 1008 via an interface, such as a video adapter 1046. Inaddition to the monitor 1044, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1002 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1048. The remotecomputer(s) 1048 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1002, although, for purposes of brevity, only a memory/storage device1050 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1052 and/orlarger networks, e.g., a wide area network (WAN) 1054. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1002 isconnected to the local network 1052 through a wired and/or wirelesscommunication network interface or adapter 1056. The adapter 1056 canfacilitate wired or wireless communication to the LAN 1052, which canalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1056.

When used in a WAN networking environment, the computer 1002 can includea modem 1058, or is connected to a communications server on the WAN1054, or has other means for establishing communications over the WAN1054, such as by way of the Internet. The modem 1058, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1008 via the serial port interface 1042. In a networkedenvironment, program modules depicted relative to the computer 1002, orportions thereof, can be stored in the remote memory/storage device1050. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

The computer 1002 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE 802.11(a, b,g, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE 802.3 or Ethernet).Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands, atan 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, for example, orwith products that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic 10BaseT wiredEthernet networks used in many offices.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “data store,” data storage,”“database,” and substantially any other information storage componentrelevant to operation and functionality of a component, refer to “memorycomponents,” or entities embodied in a “memory” or components comprisingthe memory. It will be appreciated that the memory components, orcomputer-readable storage media, described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

What has been described above includes examples of the presentspecification. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the present specification, but one of ordinary skill in theart may recognize that many further combinations and permutations of thepresent specification are possible. Accordingly, the presentspecification is intended to embrace all such alterations, modificationsand variations that fall within the spirit and scope of the appendedclaims. Furthermore, to the extent that the term “includes” is used ineither the detailed description or the claims, such term is intended tobe inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

1. A system that facilitates signaling-less dynamic call setup in awireless communication network, comprising: a monitoring component thatdetermines session state information associated with a traffic flow; anda database that stores the determined session state information at ashared memory location.
 2. The system of claim 1, wherein the monitoringcomponent is located within at least one of a user equipment (UE), thewireless communication network, an application, or a third party entity.3. The system of claim 1, wherein the database resides within at leastone of a user equipment (UE), the wireless communication network, anapplication, or a third party entity.
 4. The system of claim 1, whereinthe session state information includes at least one of a session name, amode of operation, a Quality of Experience (QoE) factor, an observedQoE, resource demand, or an observed network state, associated with thetraffic flow.
 5. The system of claim 1, further comprising, a schedulingcomponent that analyzes the session state information to at least one ofupdate an existing or create a new network policy.
 6. The system ofclaim 5, wherein the scheduling component applies the at least one ofupdated or created network policy to at least one of the traffic flow ora set of disparate traffic flows to minimize signaling between thewireless communication network and a UE.
 7. The system of claim 5,further comprising, an aggregation component that aggregates the sessionstate information stored within the database and selects data deliveredto the scheduling component, in a manner such that signaling is reduced.8. The system of claim 5, further comprising a network policy store thatstores one or more network policies associated with traffic flows in thewireless communication network, the one or more network policies areupdated by the scheduling component based on the analysis.
 9. The systemof claim 1, data pulling component that utilizes a trigger protocol tosynchronize the session state information between the database and thewireless communication network.
 10. The system of claim 1, furthercomprising an artificial intelligence component that automaticallymodifies a network policy to facilitate efficient end-to-end (ETE)resource utilization by employing one or more machine learningtechniques.
 11. A method that facilitates efficient end-to-end (ETE)resource utilization in a communication network, comprising: determiningsession state information associated with a traffic flow; and updating ashared memory location with the determined session state information.12. The method of claim 11, wherein the determining includes determiningat least one of an observed Quality of Experience (QoE), network statedynamics, a resource demand, a user preference, an applicationpreference, a service provider preference.
 13. The method of claim 12,wherein the determining the observed QoE includes monitoring andanalyzing at least one of the traffic flow, a delay, jitter, a mobilestation (MS) location, user input, or content of data delivered.
 14. Themethod of claim 11, further comprising, analyzing the session stateinformation.
 15. The method of claim 14, further comprising, updatingone or more network policies based in part on the analysis.
 16. Themethod of claim 15, further comprising, enforcing the one or morenetwork policies on the traffic flow to reduce signaling between thecommunication network and a mobile station.
 17. The method of claim 11further comprising: classifying traffic flows into one or morecategories; sampling session state information associated with a trafficflow in a category; and updating at least one network policy associatedwith a set of traffic in the category based in part on an analysis ofthe sampled information.
 18. A system that facilitates dynamicallyadjusting one or more network policies during wireless communications,comprising: means for determining session state data associated with atraffic flow between a user equipment and a communication network; meansfor storing the determined session state data, the means for storingprovides shared access to stored data; and means for modifying the oneor more network policies associated with the traffic flow based in parton an analysis of the stored session state data.
 19. The system of claim18, wherein, the means for determining determines the session state databased on at least one of an observed Quality of Experience (QoE), anobserved network state, a resource demand, a user preference, anapplication preference, a service provider preference.
 20. The system ofclaim 18, further comprising, means for synchronizing the session statedata between the means for storing and the communication network byemploying a trigger protocol.